What & why

Adds support for setting the Type property on an XMLDSIG Reference through the public SignedXml codeunit.

SignedXml already exposes the reference URI, digest method, and transforms, but not the underlying Reference.Type property. This prevents callers from creating XML signatures that require a typed reference, such as a reference to XAdES SignedProperties.

The change adds SetReferenceType(Type: Text) to SignedXml and its implementation, together with a unit test verifying that the configured value is emitted as the Type attribute of the generated <Reference> element.

Linked work

Fixes #10139

How I validated this

• I read the full diff and it contains only changes I intended.
• I built the affected app(s) locally with no new analyzer warnings.
• I ran the change in Business Central and confirmed it behaves as expected.
• I added or updated tests for the new behavior, or explained below why none are needed.

What I tested and the outcome (required — be specific: scenarios, commands, screenshots for UI changes)

• Added a unit test in SignedXmlModuleTest.Codeunit.al that initializes an XMLDSIG reference, sets its Type, computes the signature, and verifies that the generated <Reference> element contains the expected Type attribute.
• The affected Cryptography Management test module passes locally.
• No UI changes are involved.

Risk & compatibility

Low risk. The change only adds a new public procedure and delegates it to the existing underlying .NET Reference.Type property.

There are no breaking changes, data or upgrade impacts, permission changes, telemetry changes, or feature flags.